Convert remaining pip check commands to uv pip check#59670
Merged
kaxil merged 1 commit intoapache:mainfrom Dec 20, 2025
Merged
Conversation
Follow up after apache#59658 - there are few more places where canary builds used `pip check` and until the `pip` inconsistent behaviour is fixed (pypa/pip#13709) we should use `uv pip check` instead.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
kaxil
as code owners
boring-cyborg
bot
added
area:dev-tools
area:production-image
kaxil
approved these changes
Dec 20, 2025
amoghrajesh
approved these changes
Dec 20, 2025
kaxil
pushed a commit
to astronomer/airflow
that referenced
this pull request
Dec 20, 2025
Follow up after apache#59658 - there are few more places where canary builds used `pip check` and until the `pip` inconsistent behaviour is fixed (pypa/pip#13709) we should use `uv pip check` instead. (cherry picked from commit 33e6d3e)
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 33e6d3e v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
Member
Author
|
The real issue (as explained by |
Subham-KRLX
pushed a commit
to Subham-KRLX/airflow
that referenced
this pull request
Jan 2, 2026
Follow up after apache#59658 - there are few more places where canary builds used `pip check` and until the `pip` inconsistent behaviour is fixed (pypa/pip#13709) we should use `uv pip check` instead.
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 6, 2026
Follow up after #59658 - there are few more places where canary builds used `pip check` and until the `pip` inconsistent behaviour is fixed (pypa/pip#13709) we should use `uv pip check` instead. (cherry picked from commit 33e6d3e)
61 tasks
stegololz
pushed a commit
to stegololz/airflow
that referenced
this pull request
Jan 9, 2026
Follow up after apache#59658 - there are few more places where canary builds used `pip check` and until the `pip` inconsistent behaviour is fixed (pypa/pip#13709) we should use `uv pip check` instead.
jhgoebbert
pushed a commit
to jhgoebbert/airflow_Owen-CH-Leung
that referenced
this pull request
Feb 8, 2026
Follow up after apache#59658 - there are few more places where canary builds used `pip check` and until the `pip` inconsistent behaviour is fixed (pypa/pip#13709) we should use `uv pip check` instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow up after #59658 - there are few more places where canary builds used
pip checkand until thepipinconsistent behaviour is fixed (pypa/pip#13709) we should useuv pip checkinstead.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.